home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group00b.txt
/
000085_icon-group-sender_Fri Oct 20 08:00:39 2000.msg
< prev
next >
Wrap
Internet Message Format
|
2001-01-03
|
1KB
Return-Path: <icon-group-sender>
Received: (from root@localhost)
by baskerville.CS.Arizona.EDU (8.11.1/8.11.1) id e9KExrO13833
for icon-group-addresses; Fri, 20 Oct 2000 07:59:54 -0700 (MST)
Message-Id: <200010201459.e9KExrO13833@baskerville.CS.Arizona.EDU>
Date: Fri, 20 Oct 2000 09:20:59 -0400 (EDT)
From: Taybin Rutkin <trutkin@black.clarku.edu>
To: Gregg Townsend <gmt@cs.arizona.edu>
cc: icon-group@cs.arizona.edu
Subject: Re: Pipes in Icon
Errors-To: icon-group-errors@cs.arizona.edu
Status: RO
Content-Length: 621
On Thu, 19 Oct 2000, Gregg Townsend wrote:
> > From: Taybin Rutkin <trutkin@black.clarku.edu>
> >
> > ...What you're doing is creating a file at /usr/bin/xyz that is a pipe.
>
> No, this is a misunderstanding of how Icon's open(..., "p") works. It
> opens a pipe to a process; it doesn't create a named pipe. That does
Yeah, I realized I misunderstood the semantics after I reread that
chapter. I think the semantics are too different from the semantics
for opening files. Thus my confusion.
Taybin Rutkin -- trutkin@black.clarku.edu
Creativity can only be anarchic, capitalist, Darwinian
-- Umberto Eco